Abila MIP Integration
The NetForum integration for Abila MIP Fund Accounting is an export of ledger information from the NetForum batch that can be imported into Abila MIP.
Setting Up Abila MIP
Integration Classification
Class A - Baseline
- Preferred Partners provide products or services that are integrated directly into the baseline NetForum product. These integrations are developed and supported by Abila R&D. Product interface requirements will be tracked and adjustments made to baseline as required maintaining compatibility with the integrated product.
- Class A integrations are available for a fixed SAAS payment.
- In some cases, a minimal configuration charge may be required to cover any setup or customization effort (generally less than four hours) required to implement a class A integration. Most class A integrations are set up using a system option.
- In some cases a separate agreement will be required between Abila’s customer and the integration partner. In other instances, Abila will be able to make all arrangements.
- In a few cases, ongoing usages fees will be required by the integration partner in addition to the fees paid to Abila.
Client Tasks and Requirements
To integrate NetForum Enterprise with Abila MIP
- You must have Abila MIP accounting software installed.
- You must know how to import G/L files into Abila MIP.
NetForum Tasks
This integration requires System Option setup.
Baseline File Layout
Sample File Layout for summary system option
HSESSN BATCHNAME Imported AR 06172009 BP JV HDOC BATCHNAME Imported AR 06172009JV00001 JV DDOC BATCHNAME N 06172009JV00001 1010000000 JV 00000134000 00000000000Visa/MC Clearing Account 06/17/09 BATCHNAME DDOC BATCHNAME N 06172009JV00001 3200000000 JV 00000000000 00000012000Deferred Membership Revenue 06/17/09 BATCHNAME DDOC BATCHNAME N 06172009JV00001 4300000000 JV 00000000000 00000119000Event Revenue 06/17/09 BATCHNAME DDOC BATCHNAME N 06172009JV00001 4400000000 JV 00000000000 00000003000Product Revenue 06/17/09 BATCHNAME
Sample File Layout for detail system option
HSESSN BATCHNAME Imported AR 06172009 BP JV HDOC BATCHNAME Imported AR 06172009JV00001 JV DDOC BATCHNAME N 06172009JV00001 2000000000 JV 00000049500 00000000000Accounts Receivable 06/17/09 BATCHNAME DDOC BATCHNAME N 06172009JV00001 3200000000 JV 00000000000 00000012000Deferred Membership Revenue 06/17/09 BATCHNAME DDOC BATCHNAME N 06172009JV00001 2000000000 JV 00000000000 00000001500Accounts Receivable 06/17/09 BATCHNAME DDOC BATCHNAME N 06172009JV00001 2000000000 JV 00000000000 00000049500Accounts Receivable 06/17/09 BATCHNAME DDOC BATCHNAME N 06172009JV00001 2000000000 JV 00000000000 00000069500Accounts Receivable 06/17/09 BATCHNAME DDOC BATCHNAME N 06172009JV00001 2000000000 JV 00000001500 00000000000Accounts Receivable 06/17/09 BATCHNAME DDOC BATCHNAME N 06172009JV00001 1010000000 JV 00000001500 00000000000Visa/MC Clearing Account 06/17/09 BATCHNAME DDOC BATCHNAME N 06172009JV00001 4300000000 JV 00000000000 00000049500Event Revenue 06/17/09 BATCHNAME DDOC BATCHNAME N 06172009JV00001 4300000000 JV 00000000000 00000069500Event Revenue 06/17/09 BATCHNAME DDOC BATCHNAME N 06172009JV00001 1010000000 JV 00000001500 00000000000Visa/MC Clearing Account 06/17/09 BATCHNAME DDOC BATCHNAME N 06172009JV00001 1010000000 JV 00000012000 00000000000Visa/MC Clearing Account 06/17/09 BATCHNAME DDOC BATCHNAME N 06172009JV00001 1010000000 JV 00000049500 00000000000Visa/MC Clearing Account 06/17/09 BATCHNAME DDOC BATCHNAME N 06172009JV00001 2000000000 JV 00000001500 00000000000Accounts Receivable 06/17/09 BATCHNAME DDOC BATCHNAME N 06172009JV00001 2000000000 JV 00000012000 00000000000Accounts Receivable 06/17/09 BATCHNAME DDOC BATCHNAME N 06172009JV00001 4400000000 JV 00000000000 00000001500Product Revenue 06/17/09 BATCHNAME DDOC BATCHNAME N 06172009JV00001 1010000000 JV 00000069500 00000000000Visa/MC Clearing Account 06/17/09 BATCHNAME DDOC BATCHNAME N 06172009JV00001 2000000000 JV 00000000000 00000001500Accounts Receivable 06/17/09 BATCHNAME DDOC BATCHNAME N 06172009JV00001 2000000000 JV 00000000000 00000012000Accounts Receivable 06/17/09 BATCHNAME DDOC BATCHNAME N 06172009JV00001 4400000000 JV 00000000000 00000001500Product Revenue 06/17/09 BATCHNAME DDOC BATCHNAME N 06172009JV00001 2000000000 JV 00000069500 00000000000Accounts Receivable 06/17/09 BATCHNAME
When the BatchExportMethod is set to detail the detail export file contains a row for each ledger record created from the batch close process. When the BatchExportMethod is set to summary only one row appears in the detail export file for each unique G/L Account. Generally, Abila recommends exporting in summary rather than detail.
Usage and Instructions
Once the file is generated after the post batch process from the NetForum batch profile, staff should go to the MIP and import the file.
Additional Services
If the file layout shown above does not meet your requirements and you require Abila to make a layout change, an additional fee will be charged. The fee will be based on the complexity and the content of the file layout.
Tip: This process requires that you modify the BatchExportMethod system option.